Repository navigation
fix: --update recuerda el stack + release v3.0.2 - #21
Merged
Merged
Conversation
En un proyecto sin framework detectable (TypeScript puro) o en un monorepo, --update --yes fallaba si no se repetía --stack con todas sus carpetas. El manifiesto guarda ahora los stacks; para instalaciones 3.0.0/3.0.1 se deducen de .claude/rules/kit/ (nombre y paths:). Un --stack explícito sigue mandando. Release v3.0.2: versión, CHANGELOG y pins del README/CONTRIBUTING.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release 3.0.2.
--update --yesfallaba en proyectos sin framework detectable con "No se pudo detectar el stack" si no se repetía--stack. Salió al actualizar un proyecto TypeScript puro. En un monorepo había que repetir además todas las carpetas.--yeslos acepta..claude/rules/kit/, donde el nombre de cada regla dice el stack y supaths:dice las carpetas.--stackexplícito sigue mandando.El tag
v3.0.2se crea sobremasterdespués del merge.Test plan
npm run validateen verde;npm test: 100/100 (4 nuevos: stack recordado, deducido de reglas 3.0.x, monorepo con carpetas,--stackexplícito gana).work/type-kit, instalado con 3.0.0): reutilizabackend/express, "40 ya al día" y no escribe nada.git tag -a v3.0.2sobre el commit de merge ygit push origin v3.0.2.